The ONLY thing ceptors should have to do with the new sov mechanics - scouting and tackle, that is their role that is what they should do.
No sov module (offensive or defensive) should be able to be fitted to anything smaller than a battlecruiser, it should have a fuel requirement, PG and CPU requirements as well.

There'll be no blue donut when everyone just lives as concord's renters in highsec

Small ships can play a role, the one they are designed for. Ceptors role is tackle and scouting, I have no problem with that but if you can fit one of these Entosis modules to a ceptor you are actually removing active game play.
They are immune to everything but "pilot stupid", so OP when it comes to being able to use a sov changing module.

I hate to bring up this weird little complaint, but SOV laser really reminds me of capture the flag. Nothing breaks immersion like capture the flag. The entosis laser bears no resemblance to any grand space warfare we read about in sci fi books, which is the prime reason a lot of us have come to play this game.

Don't even try a false dichotomy.

There are more alternatives to sov warfare than grinding structures endlessly and having to babysit each and every structure forever.

The 2 minute cycle time is too short, can be done at too long of a distance, and if it's available to frigates it does not give the defender any ability to respond to a pre-reinforced attack short of sitting on that structure literally all the time.

That is not an acceptable solution.

I didn't say that was my plan. My position is that any distance longer than about 40km is too large.

The most major issue is with the cycle time. Structure grinding set the bar rather too high to take a crack at owning sov. But a 2 minute cycle time and a 100 million isk module is setting the bar entirely too low.

And like I said above. Setting the bar at 2 minutes of time and a 100 million isk module is setting the bar too low.

It's too large because it permits methods of engaging the structure without committing to attacking any defenders.

With a gigantic range on it like it has, if you get a decent kiting cruiser and engage at extreme range, their only chance to deal with you is to just sit on the button with their own Entosis module contesting yours, until one of you gets bored and leaves.

That is not creating conflict. That is incentivizing a lack of conflict.

4 hours... per structure, each and every day that someone with a cov ops ship spends 2 minutes while you're asleep reinforcing them.

That's not relevant. The attacker doesn't have to be on grid for that, by all indications. The attacker only has to pop out for 2 minutes, then cloak up in a safe. If they come back and "rep" it, he does it again. If they don't, they have to waste four hours the next day, and the process starts over.

That's just an inordinate amount of babysitting.

Pretty much, as currently proposed were are talking about an endeavor in ritual sucide not an endeavor of living or not living in your sov. Aside from the fact that systems should be potentially vulnerable during all timezone, not just a window, as i have said earlier i think some form of the SBU mechanic to induce vulnerability is appropriate. Reinforcing a system should require a fleet, it shouldn't be a task that is capable of being performed by 1 man or even 5 dudes. To own sov you shouldn't need to babysit your assets 24 hours a day, or even 4 hours a day, there needs to be effort expended by the attacker, organized effort at that. 1 dude in an small hull be it bc or frigate shouldn't be capable of reinforcing a system. If the goal is to encourage pvp the current mechanics proposed do not do that, they do however encourage heavy harassment until no one can be arsed to defend sov.

I think the entosis module and time duration rather than hitpoints is good. I think id get rid of the no remote reps bit, and instead require you use 10-20 of them in order to reinforce. The smallest alliance can muster this man power, any sov holding entity or sov aspiring entity should be able to manage these range of numbers. This creates a relatively low barrier to entry, undefended sov will still fall quickly, but it requires an actual fleet and should limit the more asinine forms of useless harassment. Couple this with some sort of low hitpoint fast time vulnerability mechanic reminiscent of the SBU and I think we are well on our way to a better version of the proposed system. Taking sov shouldnt be easy mode nor should defending. Dominion favored the defender a bit to much, this favors the attacker to much. There is a happy middle in there.

A periphery is there should really be a roll for Dreads/supers and carriers in this system as at current there really isnt any other than to plop them on a command node to ensure you control at least one while your subs go to others.

You ought to know by now that most people will take the low road.

That being, to park a tanky ship with a cyno in the highslots on the button contesting it.

Did you even read what I wrote? It's vulnerable to reinforce at all times, not just prime time. But once it is reinforced, you are committed to 4 hours time tax the next day, per structure, because there is zero recourse against something that takes only two minutes without being on each and every structure 24/7.

Yeah, they can, because it takes a mere 2 minutes and people have to sleep and eat and use the bathroom. If someone lives in a system, it is not "unoccupied" just because they have to sleep.

Why do you think that owning sov should be a job, instead of a videogame?

Well, missed that part. (God, their layout for that sucks) That's better than I had realized, although still not ideal.

It still mandates babysitting your structures when you should be out using your space and doing things.

Your worthless, truesec system with an income below that of L4 missions...



But I can blame mine on the ****** mobile layout they have for that dev blog. Genuinely atrocious, but that's what I get for posting from my phone.